Determining a location of a device for calling via an access point

ABSTRACT

Methods and systems for facilitating a voice over packet (VoP) call involving a VoP device are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/732,229, filed Jun. 5, 2016, which is a continuation of U.S.application Ser. No. 14/641,203, filed Mar. 6, 2015, now U.S. Pat. No.9,055,550, which is a continuation of U.S. application Ser. No.14/224,785, filed Mar. 25, 2014, now U.S. Pat. No. 9,036,626, which is acontinuation of U.S. application Ser. No. 13/012,959, filed on Jan. 25,2011, now U.S. Pat. No. 8,724,522, which is a continuation of U.S.application Ser. No. 10/924,485 filed on Aug. 24, 2004, now U.S. Pat.No. 7,940,746. The entire contents of all of these priority applicationsare herein incorporated by reference.

FIELD OF THE INVENTION

The present invention relates to methods and systems for locating adevice connected to a network, such as to locate a Voice Over InternetProtocol (VoIP) device.

BACKGROUND

Voice Over Internet Protocol (VoIP) or Internet Protocol (IP) Telephonyis a technology that allows a user to make a telephone call over theInternet or a dedicated network in IP packets, instead of over dedicatedvoice transmission lines.

With a VoIP service, it is possible for a user to move their VoIP phoneto virtually any IP network and have the ability to make and receivecalls at their home phone number, which is commonly referred to as apersonal telephone number (TN). This is, in fact, one of the benefits ofVoIP service, whereby for example a user can take their VoIP phone withthem to a hotel with broadband Internet service and have their homephone ring in their hotel room. By contrast, traditional telephoneservice is tied to a specific location by nature of the circuit-basedtelephone network.

The problem with this new capability of VoIP, however, is that thetraditional approach utilized by emergency services personnel to locatean individual in the event of an emergency 911 call no longer worksreliably in VoIP systems. For example, a VoIP customer's location isrecorded as their billing address and all calls originating from thecustomer's VoIP phone are assumed to be originating from the homeaddress of the customer. If the customer takes the VoIP phone to asecond location, such as a shore vacation home for the weekend, and alife-threatening medical emergency prompts the customer to dial 911,then the 911 call would be routed to the Public Safety Answering Point(PSAP) in the area of the customer's billing address, not their currentaddress at the shore vacation residence.

Some VoIP service providers have attempted to solve this by routing 911calls on their VoIP network to an intermediate dispatch center thatdetermines which PSAP to route the call to. The intermediate dispatchcenter includes an operator for answering the emergency 911 call. Theoperator interrogates the caller to determine their location and thenroutes the call to the PSAP in the location of the caller. However, thisapproach can add extra time to the emergency response that can becritical to safety. Moreover, it is a labor intensive and relativelyexpensive for the service provider to maintain.

SUMMARY

Features described herein provide a method and system for determining aphysical location of a device, such as a voice over packet (VoP) device,for communications, such as voice communications, that involve an accesspoint.

In some embodiments, a profile, such as a user profile, may associate aplurality of physical locations with various access points. A voice overpacket (VoP) device may connect to one of the access points to engage invoice communications via the access point, and the profile may be usedto determine a physical location to be associated with the VoP devicefor purposes of the voice communications via the access point.

In some embodiments, the user may be prompted to confirm that the useris located at the determined physical location, and the user may alsoprovide an updated physical location. In some embodiments, the updatedphysical location may comprise spoken address information, andspeech-to-text conversion may be used. In some embodiments, an enteredphysical location may be denied in case of error.

In some embodiments, the physical locations may be street addresses. Theaccess point may be identified by a network address, or by a nickname.

This Summary merely provides non-limiting examples of features that maybe described and/or claimed herein. The Summary is not an exhaustivelisting of all claim features, and should not serve to limit any of theclaims of this patent.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a network system in accordance with one aspect of thepresent invention; and

FIG. 2 illustrates a flowchart of a method for determining a location ofa device connected to a network in accordance with one aspect of thepresent invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)

FIG. 1 illustrates a network system 10 in accordance with one aspect ofthe present invention. The network system 10 generally includes a firstaccess point 14, a second access point 16, and a network 20 such thatdata and signals communicated over the network 20 are accessible byconnected a network device 24 to one of the access points 14 and 16.

The network device 24 can be any type of computer or other item that iscapable of network communications, such as computers, servers, personaldigital assistants (PDAs), and the like. In particular, the presentinvention contemplates that the network device 24 is a Voice OverInternet Protocol (VoIP) device that is configured to make VoIPtelephone calls over the network 20. In support thereof, the system 10further includes a VoIP unit 26, a VoIP emergency location application(VELA) or processing unit 28, and a Public Safety Answering Point (PSAP)30.

The VoIP device 24 can relate to any device that is capable of makingVoIP calls. Such devices can include a number of features, including atelephone with an analog terminal adapter (ATA), a software-basedSession Initiation Protocol (SIP) phone, a stand-alone or embeddedMessage Transfer Agent (MTA) device, a videophone (whetherhardware-based or software-based), a wireless phone (generally cellularphones), a Personal Digital Assistant (PDA) with VoIP software, and thelike. Preferably, the VoIP device 24 includes a unique personaltelephone number that allows the device 24 to receive VoIP telephonecalls anytime that it is connected to the network 20.

The first and second access points 14 and 16 are nodes or other featuresthat are configured to connect the network device 24 to the network 20.The system 10 shown in FIG. 1 only indicates two access points 14 and16, but it is contemplated that the system 10 may include any number ofaccess points in any number of geographical areas. Preferably, a networkaddress, such as an IP address, is associated with each access point toidentify its location on the network 20.

The network 20 generally relates to any configuration that permitsnetwork communication and VoIP calls, such as through the exchange ortransfer of electronic signals and packets over private IP networks, theInternet, or public switching telephone network (PSTN). It can includeservers, databases, softswitches, and the like which function to enable,route, and/or control voice, video, and text-based communications andcan include items generally described as VoIP softswitches, PacketCableCall Management Servers (CMS), VoIP call servers, IP Public BranchExchanges (PBXs), SIP Proxy servers, SIP Registrar servers, SIPswitches, and the like.

The PSAP 30 generally relates to a dispatch office that routes incoming911 calls, or directly dispatches a public service department, such as afire, police, or other emergency department. Preferably, the PSAP canreceive calls over a PSTN and electronically over the Internet or otherIP networks, or through other communications means, such as satellite orother wireless communication. In particular, the PSAP may be an enhanced911 (E911) dispatch center that is capable of exchanging signals throughIP-network-based applications, such as instant messaging clients,real-time communication tools (text, audio, and/or video-based), andother non-telephone clients.

The VELA 28 is configured in accordance with the present invention tocommunicate with the network 20 and to determine the location of a useron the network 20 based on a location of the network device 24, such asby determining whether the network device 24 is at the first accesspoint 14 or the second access point 16. This can be advantageous forlocating the user in the event of an emergency, such as when the usermakes an emergency 911 call using a VoIP device from one of the accesspoints 14 and 16.

The VELA 28 preferably includes an interface 36 that is configured forexchanging signals and packets with the network 20, such as forcommunicating with the VoIP device 24 and/or the PSAP 30 by exchangingsignals and packets over the network to one or more of the access points14 and 16. Preferably, the interface 36 includes an Interactive VoiceResponse (IVR) unit, Text to Speech (TTS), and/or a Speech to Text (STT)unit, which enables the interface 36 to convert speech received by theinterface to electronic signals and to similarly output electronicsignals to speech, such as to communicate with the user through the VoIPdevice 24. In particular, the interface 36 is able to output and receivevoice and touch-tone signals to and from the VoIP device 24 so that theVELA 28 can communicate verbally with the user through a dialogue andrecord the responses of the user thereto.

The VELA 28 can be configured to route calls to the PSAP 30 via the PSTNusing legacy methods of call networking/termination, to route calls viathe public Internet or private Internet Protocol (IP) peering point, andto route calls to multiple interfaces of the PSAP 30, such as a primaryinterface preference and one or more secondary interfaces, based uponthe PSAP's capabilities and preferences or the service provider'spreferences. In addition, the VELA 28 can contact the secondaryinterface if the primary interface is not reachable for some reason,such as network congestion, network failure, etc.

The VELA 28 preferably includes a processor 38 and a memory 40 forcontrolling operation of the interface 36 and for executing otherapplications and strategies, which preferably includes a 911 callrouting/query response application for transferring 911 calls from theaccess point to the PSAP associated with a location of the user, asdescribed below in more detail. The VELA 28 can include other optionalfeatures, such as a web interface application configured to enable userlocation configuration, selection, and/or confirmation, and avideo/graphic interface application configured to enable user locationconfiguration, selection, and/or confirmation via a textual or graphicalinterface on a particular type of device (cellular phone screen, videophone screen, etc.).

The VELA 28 can optionally detect the type of network device 24 basedupon information derived from its connection to the network 20. When oneof these devices with graphical capabilities is used, the VELA 28 can beconfigured to, instead of initiating an out-dial, initiate a multimediamessage to the user's device or present that device with a graphicalinterface. The user can respond to that message by pressing buttons ontheir device, clicking on the interface, or otherwise interacting withthe graphical user interface or multimedia message. This interface maytake several forms in the future but may be HTML-based, XML-based, orVoiceXML-based using today's technologies.

The VoIP unit 26 is a processing unit configured to permit and/orcontrol VoIP communications. It can include any number of features,including memory and processors (not shown) that communicate with thenetwork 20 for executing a VoIP application, such as a VoIP telephonecall. In general, the system is configured to route calls to the VoIPdevice 24 based on the telephone number assigned to it so that a usercan receive calls on the telephony device at any access point 14 and 16on the network 20 that is in communication with the VoIP unit 26.

The system 10 shown in FIG. 1 is only provided for exemplary purposesand is not intended to limit the scope of the present invention. Rather,the present invention contemplates that the system 10 may include moreor less features than those shown in FIG. 1. In particular, the VoIPdevice 24 and each of the access points 14 and 16 are illustrated asseparate items, however, the present invention contemplates that anaccess point may be integrated into the VoIP device 24 and, in addition,that these two items may be further integrated into a fixed or portablecommunications and/or computing device.

FIG. 2 illustrates a flowchart 50 of a method for locating the networkdevice (VoIP device) when it is connected to a network. The method isadvantageous in locating the user in the event of an emergency 911 callfrom the network device 24 and for routing the emergency 911 call to thePSAP 30 associated with the location of the user.

Block 54 relates to provisioning a user for operation with the VELA. Theprovisioning can include any number of features, and generally comprisescreating and storing a user profile in the database of the VELA. Theuser profile can be created by an operator inputting the user'sinformation into the VELA, by the user inputting the informationthemselves, such as through a graphical user interface (GUI) or webpage, and/or automatically by querying the VoIP device when it isconnected to the network, which is advantageous for determining the IPaddress and network hops associated with the access point to which theuser connects the VoIP device, as it may be difficult for the user oroperator to input this information. Optionally, block 54 can be skippedand the user profile can be created dynamically upon connecting the VoIPdevice to one of the access points.

The user profile preferably identifies the user with a telephone numberand includes additional location information, such as a physical address(city, state, zip code, apartment number, etc.) and network address (IPaddress and network hops) for the access point from which the userintends to connect to the network for making VoIP telephone calls. Thenetwork address is associated with the physical address as the physicaladdresses are more unique than the network addresses. This is becausethe network addresses may not, by nature of them being shared acrosswhat may be a small or large area and one or many people, be at the samelocation as the user, or at least within a small enough area relative tothe access point associated with the user that emergency personnel wouldbe able to locate the user in an emergency. Network addresses may alsobe dynamically assigned, such that the same physical address will showup at different network addresses over time. The physical locationindicates where the user is located when connecting to the access pointassociated with the current network address so that the user can belocated in the event of an emergency 911 call.

Multiple entries can be made in the user profile if the user intends touse the VoIP device at multiple locations on the network. Preferably, anickname or another unique identifier is provided if the user profileincludes multiple residences or locations for the user so that eachlocation can be easily distinguished. For example, the user may intendto use the VoIP device at home, at a beach vacation home, and at work.In which case, the user profile is provisioned with physical and networkaddress for each of the locations.

Block 58 relates to connecting the VoIP device to the network, such asif the user intends to make a call or if the user is merely connectingthe device to the network to receive calls, which may occur in the actof turning on or plugging in a device. Upon connecting to the network orin response to a message from the VELA, the VoIP device sends a messageto the VELA that includes the telephone number assigned with the VoIPdevice. The VELA analyzes the message to determine the IP address of theaccess point to which the VoIP device is connected and to determine anynetwork hops between the access point and the VELA, such as bytracerouting the IP address to determine the network hops. Thisinformation is then stored in the memory of the VELA for use indetermining a location of the user. Depending upon the results of thistransaction, the user may be queried by the VELA to confirm his/hercorrect physical location, select from a list of locations which may ormay not be sorted based upon the VELA's best estimate of the location,or choose to configure a new location in the VELA.

Block 62 relates to determining a current location for the user based onthe telephone number and network address determined in block 58.Initially, the VELA uses the telephone number to search the database fora user profile that includes the same telephone number, i.e. to match auser profile with the telephone number. Once the user profile islocated, the VELA compares the network address determined in block 58with the network addresses in the user profile. If one of the networkaddresses matches, the VELA pulls the associated physical address andcontrols the interface to contact the user, such as through an out-goingcall or other message to the user and/or their telephony device. Theuser is then asked whether the physical address corresponds with thecurrent location of the user. If the user to determine their location.The location is denied, for example, if there is an error during theinputting of the physical location to the user profile, if the userintends to be at a different location but maintains the use of the sameaccess point, and if the user failed to provide a physical address inthe user profile. In response to the denial, the VELA interrogates theuser further to determine the physical address that they desire toassociate with the network address. This information is then stored inthe user profile so that it is available the next time the user connectsto the network and the current location of the user is noted.

If none of the network addresses in the user profile match the networkaddress determined in block 58, then the user is in an unknown or newlocation. In which case, the VELA controls the interface to contact theuser, such as through an out-going call or message, to create an entryfor the unknown network ID. The entry is similar to those describedabove, in that the user is questioned by the VELA to determine aphysical address and nickname for association with the unknown networkaddress. Once the entry is complete, the physical address associatedwith the new entry is added to the user's profile and noted as thecurrent location of the user.

The dialogue to determine the location of the user, as described above,can take any number of forms. For example, the VELA can be configured toprovide the following sequential dialogue:

1. This is the 911 Service Application calling. We were unable toautomatically determine your location. Please tell us where your phoneis connected so that we can connect your call appropriately in case youhave an emergency.

a. Press 1 now if you are calling from “Home.”

i. 1 pressed, You are calling from “Home.”

ii. If this is incorrect, press # to go back to the main menu.

iii. If this is correct, press 1 now or hangup.

i. 1 pressed, You are calling from “Home.”

ii. If this is incorrect, press # to go back to the main menu.

iii. If this is correct, press 1 now or hangup.

iv. If the address of this location has changed, press 2 now to recordthe new address.

b. Press 2 now if you are calling from “Beach House.”

i. 2 pressed, You are calling from “Beach House.”

ii. If this is incorrect, press # to go back to the main menu.

iii. If this is correct, press 1 now or hangup.

iv. If the address of this location has changed, press 2 now to recordthe new address. (Speech to Text engine invoked.)

c. Press 3 now if you are calling from “Work.”

i. 3 pressed, You are calling from “Work.”

ii. If this is incorrect, press # to go back to the main menu.

iii. If this is correct, press 1 now or hangup.

iv. If the address of this location has changed, press 2 now to recordthe new address.

d. Press 4 now if you are calling from a new location.

i. We need a nickname for this location, such as “Home” or “BeachHouse.” Please speak the nickname of your location now.

ii. We need a house number for this location. Please speak the numbernow or use your keypad.

iii. We need a street for this location. Please speak the street now.

iv. We need a city for this location. Please speak the city now.

v. We need a State for this location. Please speak the State now.

vi. We need a ZIP Code for this location. Please speak the ZIP Code nowor use your keypad. (The ZIP Code could be used to avoid having to askfor the city and state, if desired.)

The VELA can also be configured with a location matching application(LMA) to facilitate locating the user. In general, the LMA is a processof matching network address determined upon connection of the VoIPdevice to the network addresses in the user profile when the networkaddresses fails to exactly match, such as if the user is at the samephysical location but using a different access point or an access pointthe utilizes multiple network address. The VELA utilizes the LMA topredictively attempt to match the network address (location of the user)by executing the following logical operations:

1. Does the current network address detected match a network address inthe user profile? If so, match the current network address to thecorresponding network address in the user profile and dialogue with theuser to determine that the physical address associated therewithcorresponds with the current location of the user, if not, proceed tonext step.

2. VELA performs a traceroute on the current network address and recordsevery hop in the traceroute. Does the first hop of the traceroute matchany of the hops (first or otherwise) for the other network addresses inthe user profile. If so, match the current network address to thecorresponding network address in the user profile and dialogue with theuser to determine the physical address associated therewith correspondswith the current location of the user, if not, proceed to next step.

3. Does the second hop of the traceroute match any of the hops in theLocation Database for the user. If so, match the current network addressto the corresponding network address in the user profile and dialoguewith the user to determine the physical address associated therewithcorresponds with the current location of the user, if not, proceed tonext step with the remainder of the hops recorded by the trace route.

As described above, the LMA utilizes intermediate network hops for thecurrent network address of the user to locate the physical address ofthe user. This can be advantageous to narrow down a geographical area inwhich the user is located. For example, the physical address of the usercan be approximated by the intermediate network hops if they match withany of the intermediate network hops in the user profile.

Block 66 relates to the user making an emergency 911 call. The emergencycall is recognized by the VELA and routed to the appropriate PSAP basedupon the location of the user determined in block 62. Each time the userconnects their VoIP device to another access point, the process above isrepeated to determine the location of the user. As such, anytime theuser makes an emergency 911 call the VELA is able to locate the user androute the call to the appropriate PSAP. Preferably, the VELA includeslogic or memory maps that facilitate locating the appropriate PSAP. Forexample, the VELA may include a database of PSAPs that are associatedwith either the physical address or the network address in the varioususer profiles.

When a user dials 911, the softswitch routes the call to the VELA, whichroutes the call to the appropriate PSAP (see PSAP Interface TechnicalOptions below), based upon the user's current location. No call to anintermediate dispatch center is needed. Alternatively, the softswitchcould perform a query to the VELA to obtain the current PSAP for theVoIP user's TN, passing this information back to the softswitch andenabling the softswitch to complete the call itself.

While embodiments of the invention have been illustrated and described,it is not intended that these embodiments illustrate and describe allpossible forms of the invention. Rather, the words used in thespecification are words of description rather than limitation, and it isunderstood that various changes may be made without departing from thespirit and scope of the invention.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice and from a voice over packet (VoP) device via an access point, amessage associated with VoP calling via the access point, wherein themessage comprises information indicating a telephone number associatedwith the VoP device; determining, based on a profile associated with theinformation indicating the telephone number, an associated callingdevice physical location for VoP calling by the VoP device; causingdisplay, via the VoP device, of a graphical interface indicating theassociated calling device physical location for VoP calling by the VoPdevice; receiving, from the VoP device and after the causing the displayof the graphical interface, a message comprising a calling devicephysical location to be used for VoP calling by the VoP device; andfacilitating a VoP call involving the VoP device.
 2. The method of claim1, wherein the calling device physical location to be used for VoPcalling by the VoP device corresponds to the associated calling devicephysical location for VoP calling by the VoP device.
 3. The method ofclaim 1, wherein the graphical interface comprises a markuplanguage-based graphical user interface.
 4. The method of claim 1,further comprising: locating the profile by conducting a database searchusing the telephone number.
 5. The method of claim 1, furthercomprising: causing storage, in the profile, of the calling devicephysical location to be used for VoP calling by the VoP device.
 6. Themethod of claim 1, further comprising: causing display of a list ofphysical locations, wherein the calling device physical location to beused for VoP calling by the VoP device is from the list of physicallocations.
 7. The method of claim 1, wherein the graphical interfaceenables user confirmation of the associated calling device physicallocation for VoP calling by the VoP device.
 8. The method of claim 1,further comprising: detecting, by the computing device, a device type ofthe VoP device.
 9. The method of claim 1, wherein the VoP device is awireless device.
 10. The method of claim 1, wherein the VoP device is aSession Initiation Protocol (SIP)-capable device.
 11. The method ofclaim 1, wherein the message associated with VoP calling via the accesspoint is sent by the VoP device after the VoP device connects to theaccess point.
 12. The method of claim 1, wherein causing the display ofthe graphical interface comprises: sending, by the computing device andto the VoP device, the graphical interface.
 13. The method of claim 1,wherein the calling device physical location to be used for VoP callingby the VoP device comprises a confirmed physical location.
 14. Themethod of claim 1, further comprising receiving, from an operator andfor a user of the VoP device, the associated calling device physicallocation for VoP calling by the VoP device.
 15. The method of claim 1,wherein the graphical interface comprises a graphical web interface. 16.An apparatus comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe apparatus to: receive, from a voice over packet (VoP) device via anaccess point, a message associated with VoP calling via the accesspoint, wherein the message comprises information indicating a telephonenumber associated with the VoP device; determine, based on a profileassociated with the information indicating the telephone number, anassociated calling device physical location for VoP calling by the VoPdevice; cause display, via the VoP device, of a graphical interfaceindicating the associated calling device physical location for VoPcalling by the VoP device; receive, from the VoP device and aftercausing the display of the graphical interface, a message comprising acalling device physical location to be used for VoP calling by the VoPdevice; and facilitate a VoP call involving the VoP device.
 17. Theapparatus of claim 16, wherein the calling device physical location tobe used for VoP calling by the VoP device corresponds to the associatedcalling device physical location for VoP calling by the VoP device. 18.The apparatus of claim 16, wherein the graphical interface comprises amarkup language-based graphical user interface.
 19. The apparatus ofclaim 16, wherein the instructions, when executed by the one or moreprocessors, further cause the apparatus to: locate the profile byconducting a database search using the telephone number.
 20. Theapparatus of claim 16, wherein the instructions, when executed by theone or more processors, further cause the apparatus to: cause storage,in the profile, of the calling device physical location to be used forVoP calling by the VoP device.
 21. The apparatus of claim 16, whereinthe instructions, when executed by the one or more processors, furthercause the apparatus to: cause display of a list of physical locations,wherein the calling device physical location to be used for VoP callingby the VoP device is from the list of physical locations.
 22. Theapparatus of claim 16, wherein the graphical interface enables userconfirmation of the associated calling device physical location for VoPcalling by the VoP device.
 23. The apparatus of claim 16, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: detect a device type of the VoP device.
 24. Theapparatus of claim 16, wherein the VoP device is a wireless device. 25.The apparatus of claim 16, wherein the VoP device is a SessionInitiation Protocol (SIP)-capable device.
 26. The apparatus of claim 16,wherein the message associated with VoP calling via the access point issent by the VoP device after the VoP device connects to the accesspoint.
 27. The apparatus of claim 16, wherein the instructions, whenexecuted by the one or more processors, further cause the apparatus to:send the graphical interface to the VoP device as part of causing thedisplay of the graphical interface.
 28. The apparatus of claim 16,wherein the calling device physical location to be used for VoP callingby the VoP device comprises a confirmed physical location.
 29. Theapparatus of claim 16, wherein the instructions, when executed by theone or more processors, further cause the apparatus to receive, from anoperator and for a user of the VoP device, the associated calling devicephysical location for VoP calling by the VoP device.
 30. The apparatusof claim 16, wherein the graphical interface comprises a graphical webinterface.
 31. A method comprising: sending, by a voice over packet(VoP) device and to a computing device via an access point, a messageassociated with VoP calling via the access point, wherein the messagecomprises information indicating a telephone number associated with theVoP device; causing display of a graphical interface indicating, basedon a profile associated with the information indicating the telephonenumber, an associated calling device physical location for VoP callingby the VoP device; receiving, from a user and via the graphicalinterface, a calling device physical location to be used for VoP callingby the VoP device; sending, by the VoP device and to the computingdevice, a message comprising the calling device physical location to beused for VoP calling by the VoP device; and engaging, by the VoP device,in a VoP call via the access point.
 32. The method of claim 31, whereinthe calling device physical location to be used for VoP calling by theVoP device corresponds to the associated calling device physicallocation for VoP calling by the VoP device.
 33. The method of claim 31,wherein the graphical interface comprises a markup language-basedgraphical user interface.
 34. The method of claim 31, furthercomprising: causing, by the VoP device, output of a list of physicallocations, wherein receiving the calling device physical location to beused for VoP calling by the VoP device comprises receiving, via thegraphical interface, user input indicating a user selection from thelist of physical locations.
 35. The method of claim 31, wherein thegraphical interface enables user confirmation of the associated callingdevice physical location for VoP calling by the VoP device.
 36. Themethod of claim 31, wherein the sending of the message associated withVoP calling via the access point is performed by the VoP device in afterthe VoP device connects to the access point.
 37. The method of claim 31,wherein the VoP device is a wireless device.
 38. The method of claim 31,wherein the VoP device is a Session Initiation Protocol (SIP)-capabledevice.
 39. The method of claim 31, further comprising: receiving, bythe VoP device and from the computing device, the graphical interface.40. The method of claim 31, wherein the calling device physical locationto be used for VoP calling by the VoP device comprises a confirmedphysical location.
 41. The method of claim 31, wherein the graphicalinterface comprises a graphical web interface.
 42. A voice over packet(VoP) device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe VoP device to: send, to a computing device and via an access point,a message associated with VoP calling via the access point, wherein themessage comprises information indicating a telephone number associatedwith the VoP device; cause display of a graphical interface indicating,based on a profile associated with the information indicating thetelephone number, an associated calling device physical location for VoPcalling by the VoP device; receive, from a user and via the graphicalinterface, a calling device physical location to be used for VoP callingby the VoP device; send, to the computing device, a message comprisingthe calling device physical location to be used for VoP calling by theVoP device; and engage in a VoP call via the access point.
 43. The VoPdevice of claim 42, wherein the calling device physical location to beused for VoP calling by the VoP device corresponds to the associatedcalling device physical location for VoP calling by the VoP device. 44.The VoP device of claim 42, wherein the graphical interface comprises amarkup language-based graphical user interface.
 45. The VoP device ofclaim 42, wherein the instructions, when executed by the one or moreprocessors, cause the VoP device to: cause display of a list of physicallocations; and receive, via the graphical interface, user inputindicating user selection, from the list of physical locations, of thecalling device physical location to be used for VoP calling by the VoPdevice.
 46. The VoP device of claim 42, wherein the graphical interfaceenables user confirmation of the associated calling device physicallocation for VoP calling by the VoP device.
 47. The VoP device of claim42, wherein the instructions, when executed by the one or moreprocessors, cause the VoP device to send the message associated with VoPcalling via the access point after the VoP device connects to the accesspoint.
 48. The VoP device of claim 42, wherein the VoP device is awireless device.
 49. The VoP device of claim 42, wherein the VoP deviceis a Session Initiation Protocol (SIP)-capable device.
 50. The VoPdevice of claim 42, wherein the instructions, when executed by the oneor more processors, further cause the VoP device to: receive, from thecomputing device, the graphical interface.
 51. The VoP device of claim42, wherein the calling device physical location to be used for VoPcalling by the VoP device comprises a confirmed physical location. 52.The VoP device of claim 42, wherein the graphical interface comprises agraphical web interface.
 53. A system comprising: a computing device anda voice over packet (VoP) device, wherein the computing devicecomprises: one or more processors; and memory storing instructions that,when executed by the one or more processors, cause the computing deviceto: receive, from the VoP device via an access point, a messageassociated with VoP calling via the access point, wherein the messagecomprises information indicating a telephone number associated with theVoP device; determine, based on a profile associated with theinformation indicating the telephone number, an associated callingdevice physical location for VoP calling by the VoP device; receive,from the VoP device, a message comprising a calling device physicallocation to be used for VoP calling by the VoP device; and facilitate aVoP call involving the VoP device; and wherein the VoP device comprises:one or more processors; and memory storing instructions that, whenexecuted by the one or more processors of the VoP device, cause the VoPdevice to: cause display of a graphical interface indicating theassociated calling device physical location for VoP calling by the VoPdevice.
 54. The system of claim 53, wherein the calling device physicallocation to be used for VoP calling by the VoP device corresponds to theassociated calling device physical location for VoP calling by the VoPdevice.
 55. The system of claim 53, wherein the graphical interfacecomprises a markup language-based graphical user interface.
 56. Thesystem of claim 53, wherein the instructions in the memory of thecomputing device, when executed by the one or more processors of thecomputing device, further cause the computing device to: locate theprofile by conducting a database search using the telephone number. 57.The system of claim 53, wherein the instructions in the memory of thecomputing device, when executed by the one or more processors of thecomputing device, further cause the computing device to: cause storage,in the profile, of the calling device physical location to be used forVoP calling by the VoP device.
 58. The system of claim 53, wherein theinstructions in the memory of the VoP device, when executed by the oneor more processors of the VoP device, further cause the VoP device to:cause display a list of physical locations; and receive, via thegraphical interface, user input indicating user selection, from the listof physical locations, of the calling device physical location to beused for VoP calling by the VoP device.
 59. The system of claim 53,wherein the graphical interface enables user confirmation of theassociated calling device physical location for VoP calling by the VoPdevice.
 60. The system of claim 53, wherein the instructions in thememory of the computing device, when executed by the one or moreprocessors of the computing device, further cause the computing deviceto: detect a device type of the VoP device.
 61. The system of claim 53,wherein the instructions in the memory of the VoP device, when executedby the one or more processors of the VoP device, further cause the VoPdevice to send the message associated with VoP calling via the accesspoint after the VoP device connects to the access point.
 62. The systemof claim 53, wherein the VoP device is a wireless device.
 63. The systemof claim 53, wherein the VoP device is a Session Initiation Protocol(SIP)-capable device.
 64. The system of claim 53, wherein theinstructions in the memory of the VoP device, when executed by the oneor more processors of the VoP device, further cause the VoP device to:receive, from the computing device, the graphical interface.
 65. Thesystem of claim 53, wherein the calling device physical location to beused for VoP calling by the VoP device comprises a confirmed physicallocation.
 66. The system of claim 53, wherein the instructions in thememory of the computing device, when executed by the one or moreprocessors of the computing device, further cause the computing deviceto receive, from an operator and for a user of the VoP device, theassociated calling device physical location for VoP calling by the VoPdevice.
 67. The system of claim 53, wherein the graphical interfacecomprises a graphical web interface.